home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.8 KB | 44 lines | [TEXT/GEOL] |
- INTERNET# Document Id: <44260@apple.Apple.COM>
-
- Item 7667562 24-Aug-90 12:31
-
- From: MALCOLM@APPLE.COM@INTERNET# Gateway to Internet/BITNET/UUCP
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: Re: Multiple Inheritance Ques
-
- TO REPLY, use: malcolm@Apple.COM@INTERNET#
- Using the reply function in AppleLink does not work for gatewayed E-mail yet.
-
- From: malcolm@Apple.COM (Malcolm Slaney)
- References: <6435527@AppleLink.Apple.COM>
- Lines: 21
- Organization: Apple Computer Inc, Cupertino, CA
- Newsgroups: apple.mac.app
- Path: apple!malcolm
- To: macapp.tech$@applelink.apple.com
-
-
- POWERUP.ENG@AppleLink.Apple.COM (Power Up Software,PRT) writes:
- >I've been asked more than once for an example of a situation in which multiple
- >inheritance is really useful, rather than being a means of avoiding thoughtful
- >design. I think I've come up with one, and I'd like to hear the comments of
- >anyone interested in responding.
-
- I've always thought that the Symbolics (Lisp Machine) Window System was the
- BEST example of how to use and prosper with multiple inheritance. It works
- best when you have relatively orthogonal features that want to cooperate.
-
- The canonical example is a scrollbar mixin. Types are called flavors in the
- old pre-PCL world, thus mixins are types that aren't meant to be instantiated
- on their own but instead mixed into another type. A scrollbar can be mixed
- into a window type and then when the time comes to figure out the real size
- of the window the scrollbar gets to add its width into the calculation.
-
- Needless to say, it takes a lot more effort to get the type hierarchy right
- but I think the result is worth it.
-
- Malcolm Slaney
- ATG Perception Group
-